Conversation
|
@Dimillian fixed issue for windows with threads, not getting them properly |
|
@codex review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 93ace4f8d7
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| import { | ||
| asString, | ||
| normalizeRootPath, | ||
| import { |
There was a problem hiding this comment.
This change introduces a nested import { token inside an existing import clause, which is invalid TypeScript syntax and prevents the file from parsing at all. In practice this blocks all frontend compile paths (typecheck, tests, and app build) in every environment until the import is rewritten as one valid named import from @threads/utils/threadNormalize.
Useful? React with 👍 / 👎.
2 participants
Windows threads werent working on my windows (not getting history from projects) also terminal wasnt working